Skip to content

fix: Temperature preheat command fires at correct time within long co…#2328

Merged
HellAholic merged 4 commits into
mainfrom
CURA-13115
Jun 12, 2026
Merged

fix: Temperature preheat command fires at correct time within long co…#2328
HellAholic merged 4 commits into
mainfrom
CURA-13115

Conversation

@HellAholic

@HellAholic HellAholic commented Apr 18, 2026

Copy link
Copy Markdown
Contributor

Description

For long zigzag skin (initial layer) the temperature command was firing at the beginning of the path (start of skin) rather than at the end-ish of layer 0 (with consideration for the heat up time).

The fix ensures that at the start of each path only genuinely overdue inserts are fired immediately. Inserts assigned to the current path are held until the insertTempOnTime callback reaches their time_after_path_start, preserving the intended placement regardless of how many paths the feature is split into.

image

Type of change

  • Bug fix

How Has This Been Tested?

  • Create a build -> Slice -> inspect Gcode under similar conditions with both before and after having the zigzag initial layer -> check the temperature command is inserted at the correct moment

Test Configuration:

  • Operating System: Windows 11

Checklist:

  • My code follows the style guidelines of this project as described in UltiMaker Meta
  • I have read the Contribution guide
  • I have commented my code, particularly in hard-to-understand areas
  • I have uploaded any files required to test this change

CURA-13115

…ntinuous paths

For long zigzag skin (initial layer) the temperature command was firing at the beginning of the path (start of skin) rather than at the end-ish of layer 0 (with consideration for the heat up time).

The fix ensures that at the start of each path only genuinely overdue inserts are fired immediately. Inserts assigned to the current path are held until the insertTempOnTime callback reaches their time_after_path_start, preserving the intended placement regardless of how many paths the feature is split into.
@HellAholic HellAholic added the PR: Community Contribution 👑 Community Contribution PR's label Apr 18, 2026
@github-actions

github-actions Bot commented Apr 18, 2026

Copy link
Copy Markdown
Contributor

Test Results

31 tests   31 ✅  4s ⏱️
 1 suites   0 💤
 1 files     0 ❌

Results for commit 61126e6.

♻️ This comment has been updated with latest results.

@rburema Remco Burema (rburema) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'C++ Benchmark'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.50.

Benchmark suite Current: 3b6dad2 Previous: e413060 Ratio
SimplifyTestFixture/simplify_local 1.9447085998230405 ns/iter 1.246300090173324 ns/iter 1.56

This comment was automatically generated by workflow using github-action-benchmark.

CC: Jaime van Kessel (@nallath) Jelle Spijker (@jellespijker) Erwan MATHIEU (@wawanbreton) Casper Lamboo (@casperlamboo) Saumya Jain (@saumyaj3) HellAholic

@HellAholic HellAholic changed the base branch from 5.13 to main April 20, 2026 07:51
Comment thread src/ExtruderPlan.cpp Outdated
HellAholic and others added 2 commits June 8, 2026 09:59
Co-authored-by: Remco Burema <41987080+rburema@users.noreply.github.com>
@HellAholic HellAholic marked this pull request as ready for review June 8, 2026 08:00
@HellAholic HellAholic merged commit 3f75aea into main Jun 12, 2026
56 of 61 checks passed
@HellAholic HellAholic deleted the CURA-13115 branch June 12, 2026 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR: Community Contribution 👑 Community Contribution PR's

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants